Cream of the Crop 11/Cream of the Crop 11-2.iso/bbs/ra2t_107.zip/RA_2_TAG.ENG

Text File | 1996-01-12 | 23KB | 487 lines

     ┌───────────────────────────────────────────────────────────────────┐
     │                         ▒▒▄  ▒▒▄ ▒▒▄  ▒▒▒▒▒▒▄                     │
     │                         ▒▒█  ▒▒█ ▒▒█  ▒▒█▀▒▒█                     │
     │                         ▒▒█  ▒▒▒▒▒▒█  ▒▒▒▒▒█▀                     │
     │                     ▒▒▄ ▒▒█  ▒▒█▀▒▒█  ▒▒█▀▒▒▄                     │
     │                      ▒▒▒▒█▀  ▒▒█ ▒▒█  ▒▒█ ▒▒█                     │
     │                       ▀▀▀▀    ▀▀  ▀▀   ▀▀  ▀▀                     │
     │ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄   ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ │
     │ ▒▒█▀▀▀▀ ▒▒█▀▒▒█ ▒▒█▀▀▀▀  ▀▒▒█▀▀ ▒▒█   ▒▒█ ▒▒█▀▒▒█ ▒▒█▀▒▒█ ▒▒█▀▀▀▀ │
     │ ▒▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒▒▒▒▄    ▒▒█   ▒▒█   ▒▒█ ▒▒▒▒▒▒█ ▒▒▒▒▒█▀ ▒▒▒▒▒▄  │
     │  ▀▀▀▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀    ▒▒█   ▒▒█▒▒▄▒▒█ ▒▒█ ▒▒█ ▒▒█▀▒▒▄ ▒▒█▀▀▀  │
     │ ▒▒▒▒▒▒█ ▒▒▒▒▒▒█ ▒▒█       ▒▒█    ▀▒▒▒▒█▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ │
     │  ▀▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀        ▀▀      ▀▀▀▀    ▀▀  ▀▀  ▀▀  ▀▀  ▀▀▀▀▀▀ │
     └───────────────────────────────────────────────────────────────────┘

                J.H.R. Software is a TradeMark of J.H. Rietveld.

     Copyright (c) 1992-1996 / J.H.R. Software (TM) / All rights reserved

   J.H.R. Software (TM) / Burg Elsenlaan 197 / 2282 NE / Rijswijk / Holland.

       Postbankaccount : 3625008 / ABN-Amro bankaccount : 43.15.68.383

            Phone BBS : [phone] / Phone FAX : [phone]

 ├────────────────────────────────────────────────────────────────────────────┤

 ■ 100% competable with ON_OFF_A

 ■ If you are using a previous version of this program you have to overwrite
   the *.EXE files, kill the configuration files and setup the progran with
   RA_2_SET.EXE again.

 ■ RA_2_TAG.EXE is an EXTERNAL files and newfiles lister with TAG-OPTION for
   use with RA 2.02. Fully FILEBASE support.

 ■ RA_2_TAG.EXE has a REQUEST-OPTION build in for CD-ROM.

 ■ ANSI-users TAG files with the cursorkeys and the enterkey.

 ■ This tagger has the possibility to scroll BACK. Handy if you forgot
   to tag a file and you don't want to start up the lister again!

 ■ Fully control of the TIME and KBYTES LIMITS is build in.
   The internal RATIO-check RA makes use of will be supported.

 ■ The LIST and DL security, FLAGS and NOTFLAGS are being controlled.

 ■ This program is fully MULTI-LINE and MULTI-LANGUAGE aware.

 ■ This program is fully compatible with MTS, Easytag and Filedoor.

 ■ A LOGFILE option is present. The areanumber, areaname and filepath are
   written in the RA logfile, in COMPACT or EXPANDED mode.

 ■ Files tagged and bytes will visible.
   (If more then 10 MB or higher only kbytes will be showed.)

 ■ The user definable screensize is used.
   If 23 lines, double statusbar.
   If 24 lines, single statusbar.
   If 25 lines, NO statusbar.
   If smaller than 23 or greater than 25 lines, the screen will be cleared
   remotely. This because tagged files are not correctly shown to the sysop.
   The userside is ok though!

 ├────────────────────────────────────────────────────────────────────────────┤

                                      INDEX:
                                      ------

  [ 1 ] Installation.

  [ 2 ] CFG-file and RA setup.

  [ 3 ] Limits and ratio.

  [ 4 ] View option.

  [ 5 ] Newfiles search option.

  [ 6 ] Filesearch option.

  [ 7 ] CD-ROM request option.

  [ 8 ] Registration.

  [ 9 ] Technical information.

  [10 ] Thanks to the ßetatesters...

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 1 ] Installation.

  This program makes use of 250 kbytes conventional DOS-memory.
  If you want to be able to make an optimum use of your memory the *M
  parameter should be used in RA.
  Add to the 250 kbytes DOS-memory de size of your FILES.RA file.
  This will be the total amount of memory this program makes use of and
  that makes this program work for 100%.
  If you don't have enough memory available it can happen that the last
  areas are not listed.
  A maximum of 2500 file-areas is being read. If you have more then that
  the program will not list them.

  A maximum of 100 files can be tagged ( < TAG > ).

  Install this program, menutype 7, with the following parameters:

  <path>RA_2_TAG.EXE -P:*0 -L:*N *X *M               { Filelist option }

  <path>RA_2_TAG.EXE -N: -L:*N *X *M                 { Newfile search option }

  <path>RA_2_TAG.EXE -F: -L:*N *X *M                 { Filename search option }

  <path>RA_2_TAG.EXE -K: -L:*N *X *M                 { Keyword search option }

  -P:   represents the filearea path
  -L:   represents the node
  -N:   represents the newfiles search option
  -F:   represents the filename search option
  -K:   represents the keyword search option
  -R:   represents the requested search option
  -A:   represents the number tagging like RA.

  An extra line "Use the `S` key to stop searching" is visible for the users
  when they use the NEWFILES / KEYWORD / FILENAME search options.

  -G:   can be used with the -N -F -K parameters and gives the opportunity to
        search in the current group only.
  -P:*0 can be used and gives the opportunity to search in the current area
        only.
  -E:   causes an EXTRA tagfile for those who want to keep on using FILEDOOR.
        This tagfile is written in the directory where your SET RA= variable
        points to.
  -R:   only search for requested files by username.
  -T:   with this the USERTIME LEFT is set to 3 minutes before midnight,
    which will prevent your system from being unable to run all your
    daily events, presuming that you run you daily events around midnight!

  Extra memory- and area-information is only visible with the -K: -N: -F:
  parameters.

  RA presents with *0 the filearea path
  RA presents with *N the node
  RA presents with *X the possibility to read or write the selected files
  Ra presents with *M the possibility to swap into memory

  The EXITINFO.BBS and DORINFO?.DEF and TAGFILE.RA are being read and
  written in the CURRENT directory where RA is being processed.

  The files RA_2_HLP.AS? and RA_2_INF.AS? have to be present in de directory
  in which you installed this door.
  These files can be edited as .ASC .ANS .AVT and makes it possible to create
  different files for each language you are using.
  If you are using only one language just name your files .ASC, .ANS etc.
  If you are using more languages you can name them for example .AS1, .AS2
  and so on.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 2 ] Configuration and RA setup.

  The file RA_2_SET.EXE is the setupprogram for this tagdoor.
  The '0' option has to be run ALWAYS! Otherwise this door won't work at all.
  The file RA_2_TAG.CFG is being made.
  The other options are only needed if you are running RA with more then one
  language.
  If you are using more then one language and you select for example option
  1 a special configurationfile is processed. The file-extension will be
  corresponding to the languagenumber you have selected.

  The setup consists of 4 pages.

  In the first page you can define the colours you want to use and edit the
  textparts < TAG > and [ REQ ].
  < TAG > is shown to a user if she or he selected a file for download.
  [ REQ ] is shown to a user if she or he selected a file that is cuurently
          not available for download because that file is on a CD-ROM which
          is at the moment not online.
  The REQUEST-option will be mentioned later on in this document.
  You can also activate the option if the ENTER should be used in the file-
  discription or if de | (pipeline) should be used as an ENTER.

  In the second page the position of the filename and the amount of kbytes
  can be edited. The default values (resp. 1 en 14) must be correct in most
  cases (if you ar NOT using the standard RA listformat you have to edit
  these values). If a file is being UN-TAGGED the length of de < TAG > is
  removed and the amount of kbytes is vissible again.
  The search for NEW FILES can be installed in this page at a search on a
  given amount of days or on date.
  The text in the statusbar can be edited.
  Also you can tell this program to mark the requested CD-ROM files as
  NEW FILES. The next time a user logs in he will see the requested files
  as new files (if you selected this option at 'fresh' logons).
  This will spare some time for your users...

  In the third page you can also edit some text parts in this program.
  This can be particularly useful when working with more then one language.
  The CD-ROM requestlevel is the level a CD-ROM area must have to be able to
  request a file from that area(s). This level must be EQUAL to the level that  zijn aan het level
  was given in FILES.RA to that area so a user is able to normally download a
  file and in this case REQUEST a file.
  Also you can enter the areanumber from which the requested file(s) can be
  downloaded after it has been copied into that area with RA_2_PRO.EXE.

  In the fourth page you can edit the directory or the areanumber of your
  messagebase where you can post a message to an user if he has requested a
  file or if you want to tell that specific user that the requesetd file(s)
  is available from the time the message was posted.
  If the mailing-options stay on 0 (default) there will be NO message
  posted.
  On line 1 you enter the path of your netmail directory or the local
  areanumber. In this case the sysop will be notified that someone has
  requested some file(s).
  On line 2 you enter your MAIN aka as it is mentioned in your mailer.
  On line 3 you can enter the name of the addressee (default is SysOp).
  On line 4 you can enter the nodenumber of the addressee.
  This will be the same as your main aka if you are posting this message to
  yourself. In other cases it is possible that you fill in the aka of your
  co-sysop, telling him te get into action.....
  On the last line you can enter the number of your local area, ie. 1,
  where the message RA_2_PRO.MSG will be placed to tell the user the
  requested file(s) is ready for download in group ?, area ?.
  On the last line you can activate the option if you want to use the users
  HANDLE in the file-discription or just his name.
  Remember, if the HANDLE field is not filled in the userbase, nothing will
  be added to the discription!

  In the fifth page the statusbar can be editted an user will see if he
  started this lister/tagger.
  If you want to change anything here it might be necessary to change the
  'INPUT CHARACTERS' as well!
  It is possible to delete characters from the discription.
  The advantage of this option is that if you enter characters like /\- etc.
  and the use ENTER and use | are turned off in the setup, RA_2_TAG handles
  the discription perfectly well.

  The following is being read in the RA configuration files
  ---------------------------------------------------------

  The next lines are read from the RA languagefile :

    1 -   2 - 126 - 195 - 196 - 197 - 198 - 216 - 237
  237 - 238 - 241 - 242 - 248 - 249 - 258 - 473 - 475
  601 - 602 - 604 - 606 - 607 - 609 - 618 - 627

  627 has 2 inputkeys: a DELETE-key and a CLEAR-key

  The colour of this text will be light gray. You are able to edit it and give
  the text an other colour if you like.

  FILES will be displayed as configured in RA.
  If files are not visible in the correct format you should take notice of
  the following line.

  k[0b@NE k[02@SB k[05@FDk[0D@NW#03k[09@TD#00 k[07@DF

  The little k[ with following 2 characters represent a colourcode.
  (For the rest of this line I advice you to consult your RA-documentation...)

  The EXTERNAL_ARCHIVE_VIEWER path is being read.
  If not given, the VIEW-option is omitted.

  If a file is MISSING or DELETED an user will not see that file at all.
  If a file is UNLISTED or NOT AVAILABLE it isn't visible for an user. Only
  the sysop will be able to see this file....

  If your ANSI-screens become SLOW, or if an user doesn't see them at all but
  when you login locally every thing seems to work fine you should seek for
  the solution to your fossildriver. Some fossildrivers can cause these
  problems.
  As far as I know everything works for 100% with: X00 v1.24 en X00 v1.53a.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 3 ] Limits and ratio.

  The daily ratio of time and kbytes will be processed exactly in the same
  manner as RA processes these items.
  The internal ratio-system from RA is supported.
  The LIST and DOWNLOAD security, Flags and Notflags are fully supported.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 4 ] View option.

  The external VIEW-option is operational if setup in RA.
  Fill in the path and filename of the external viewer with the parameters
  @ = path and filename, *N is the node and *M is standard.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 5 ] Newfiles search option.

  The NEWFILES SEARCH-option works in the same way as under RA but in the
  setup of this door you can make a choice between a search on DATE or on
  an amount of DAYS backwards if an user doesn't want to search for the
  new files since his last login.
  If an user hits the ENTER-key the program will stop.
  The appropriate commandline for the newfiles search is:
  RA_2_TAG.EXE -N: -L:*N -X *M.
  If you only allow a newfiles search in the current group add the
  -G parameter.
  If you only allow a newfiles search in the current filearea add the
  -P:*0 parameter.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 6 ] Filesearch option.

  The KEYWORD and FILENAME search optiions work the same as in RA.

  <path>RA_2_TAG.EXE -F: -L:*N *X *M                  { search on filename }

  <path>RA_2_TAG.EXE -K: -L:*N *X *M                  { search on keyword }

  If the search is only wanted in the current group ad the parameter -G.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 7 ] CD-ROM request option.

  With this option it is possible, if you have more CD's then drives, to
  add the contents of those CD's in your RA filebase and let an user REQUEST
  a file instead of tagging it.
  If an user tagged a file he will see < REQ > instead of < TAG >.
  Requested files will be recorded in the file TAGLIST.RA$.

  All this is possible by giving the CD-ROM-REQUEST security in the setup of
  this door (RA_2_SET.EXE). If the DOWNLOAD security for a file-area is
  equal to the CD-ROM requestlevel, the tagger will change to the request
  option by itself.
  This option overrules your downloadsecurity level in RA. If the user level
  is insufficient and the downloadsecurity is equal to the requestlevel the
  door starts up in requestmode. Don't forget to set the CD-ROM flag to YES
  for that area (RACONFIG > MANAGER > FILEAREAS).

  After an user logs off you should start the program RA_2_REQ.EXE -T:<path>
  where <path> is the directory in which the file TAGLIST.RA$ can be found,
  usualy this will be C:\RA.
  RA_2REQ.EXE gets all the information about the requested files from the
  file TAGLIST.RA$ and produces a file !REQUEST.LST in the directory where
  RA_2_REQ.EXE was executed from.
  If !REQUEST.LST already exists the new information is added to the file.
  In the setupprogram you can activate the possibility to write a message to
  yourself or for example to your co-sysop telling you that somebody requested
  one or more files.

  Daily you should run the program RA_2_PRO.EXE -T:<path>.
  <path> is the directory where !REQUEST.LST can be found.
  RA_2_PRO.EXE makes it possible for you to copy the requested files from
  your CD's into the filearea you mentioned in the setup.

  The file !REQUEST.LST (max. 500 lines) is being read, together with
  CONFIG.RA, RA_2_TAG.CFG and FILES.RA.
  RA_2_PRO first of all searches for the requested files on the CD that is
  online. If not, the areaname and areanumber is reported to you (setup!) so
  you can insert the correct CD in your drive.
  Maybe it is wise to give your CD's a number. This number should be
  corresponding to a certain filearea, for example CD 1 = area 100 etc..
  This program can NOT be run in an event. If you have lots of CD's you'll
  become a real disc-jockey....

  If a file already exists in the specific area you will be asked if it
  should be overwritten. If the answer is NO the program still updates the
  filebase with the current date.
  If you lend out one of your CD's (never do!) it could happen that a requested
  file can't be found. No problem, press ESC and the request will simply be
  skipped.

  The downloadcounters and the last-download-date where you copied the files
  from will be updated. The same will be done in the area you copied the files
  to. This option can be selected in the setup.
  The requested Files will now be seen as NEW FILES.
  It is wise to run RAFILE SORT <areanumber> after you copied the requested
  files. If you don't do this it could happen that the files will not be seen
  as NEW.
  After all the requests are processed, the file !REQUEST.LST will be deleted.

  If you are using FILEMGR as your TOSSER the following is important.
  If you are using version v0.60 (08-14-94) or an older version, it is
  NECESSARY to sort ALL areas to be sure that new files are marked as new
  files. This program uses the IDX record and has some trouble with the
  wrong date notation Filemgr causes.
  (In the next version of Filemgr this bug will be fixed.)

  If you have selected to update the copied files in the setup  you can specify
  in RACONFIG whether or not you want these files to be deleted after say
  seven days. You can manage this option by using RAFILE CLEAN /KM and after
  that run RAFILE COMPRESS.
  If you didn't choose for the update option you can only delete the files
  from the filebase by using the FILEDATE.

  The last thing RA_2_PRO.EXE does is sending a message, RA_2_PRO.MSG, to the
  user(s) to tell them, the next time they visit your system, the requested
  files are ready for download in a specifi area.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 8 ] Registration.

  This program is SHAREWARE and may be used freely for 31 days.

  After that period you have to registrate by using de file REGISTER.ENG.
  This file tells you all about the price and how to get your registration.

 ├────────────────────────────────────────────────────────────────────────────┤

  [ 9 ] Technical information.

  The search for newfiles and the search on filename is done with the help of
  the IDX record. The search on keyword is doen with the help of the IDX and
  TXT records.
  If a file is found ALL information from the HDR and TXT records is read.

  The special tagfile for Filedoor users is build as is written in the
  structurefile as is coming with Filedoor.

  The RA tagfile is build as is written in the RA documentation.

  The structure of the tagfile with CD-ROM requestinformation is equal to the
  RA tagfile. The only difference is, that the first record is filled with:
            Name := first 12 characters of the username
        Password := last 15 characters of the username
            Cost := Userrecord position
        XferTime := Userrecord position

  With this information the program is able to see if the tagfile 'belongs'
  to a specific user and the RA_2_REQ utility knows which user should be
  posted a message to.

  This program is written with the help of: J_COM_01.ARJ and J_UNI_09.ARJ.
  Both files are requestable from my system.

 ├────────────────────────────────────────────────────────────────────────────┤

  [10 ] Special thanks to the following ßetatesters...

  Thank you Peter Hoek > MarLin Software <
  for writing the SETUP-program.

  Thank you Mike van der Meer > Westbroek BBS <
  for writing this documentation and helping me out with some linguistic
  problems.

  Thank you Ron Huiskes < Interface >
  for testing  this program multiline (4 lines) and your help with writing
  and reading the RA filebase.

  Also thanks to the following persons for their ability to test this program:

  Username :           BBSname:              Nodenumber:  BBSphone:
  ---------------------------------------------------------------------
  Ron Huiskes          > INTERFACE <         2:281/506    31-70-3361380
  Mike van der meer    Westbroek BBS         2:281/536    31-70-3500492
  Rina de Jong         The Cauldron          2:281/216    31-2522-20573
  Manuel van Lint      ShortCircuit BBS      2:285/220    31-76-415593
  Jan-Jacob Bakker     JJB-BBS               2:282/110    31-5212-1829
  Matthijs in `t anker Consolation BBS       2:281/541    31-70-3563985
  Maurice Pasman       The_Twilight Phone    111:313/408  31-10-4614202
  Hans Snijder         Independence BBS      2:285/102    31-20-6476992
  Peter Vernout        Bull's eye bbs        2:2801/159   31-23-240281
  Freddie Wakanno      The FCS-BBS           111:311/205  31-50-717831
  Marco van de Panne   Contact BBS           111:3133/105 31-70-3674425
  Edwin van Ewijk      Contact BBS II        197:200/600  31-70-3674425
  Rien Dijk            Telecenter Groningen  111:311/107  31-50-265270
  Ron Vos              Harbour BBS           111:319/508  31-2290-70143

 ├────────────────────────────────────────────────────────────────────────────┤

     ┌───────────────────────────────────────────────────────────────────┐
     │                         ▒▒▄  ▒▒▄ ▒▒▄  ▒▒▒▒▒▒▄                     │
     │                         ▒▒█  ▒▒█ ▒▒█  ▒▒█▀▒▒█                     │
     │                         ▒▒█  ▒▒▒▒▒▒█  ▒▒▒▒▒█▀                     │
     │                     ▒▒▄ ▒▒█  ▒▒█▀▒▒█  ▒▒█▀▒▒▄                     │
     │                      ▒▒▒▒█▀  ▒▒█ ▒▒█  ▒▒█ ▒▒█                     │
     │                       ▀▀▀▀    ▀▀  ▀▀   ▀▀  ▀▀                     │
     │ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄   ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ │
     │ ▒▒█▀▀▀▀ ▒▒█▀▒▒█ ▒▒█▀▀▀▀  ▀▒▒█▀▀ ▒▒█   ▒▒█ ▒▒█▀▒▒█ ▒▒█▀▒▒█ ▒▒█▀▀▀▀ │
     │ ▒▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒▒▒▒▄    ▒▒█   ▒▒█   ▒▒█ ▒▒▒▒▒▒█ ▒▒▒▒▒█▀ ▒▒▒▒▒▄  │
     │  ▀▀▀▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀    ▒▒█   ▒▒█▒▒▄▒▒█ ▒▒█ ▒▒█ ▒▒█▀▒▒▄ ▒▒█▀▀▀  │
     │ ▒▒▒▒▒▒█ ▒▒▒▒▒▒█ ▒▒█       ▒▒█    ▀▒▒▒▒█▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ │
     │  ▀▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀        ▀▀      ▀▀▀▀    ▀▀  ▀▀  ▀▀  ▀▀  ▀▀▀▀▀▀ │
     └───────────────────────────────────────────────────────────────────┘